[DE]Momaw

So, for DX11 mode,  normally the video driver will build a cache of all the graphical shaders that a level will use.  A huge amount of CPU usage is a one-time thing where your video driver will compile all the shaders, and then put them in the cache so that it doesn't need to do it again next time you play.  If you're seeing this happen repeatedly, then it probably means that your shader cache isn't working correctly.

Check your GPU control panel and make sure that you have not disabled the shader cache nor constrained it. This should be on Default unless you have very specific reasons not to.  Likewise make sure that your storage device is not dangerously full.

Your shader cache for warframe might also be corrupted. You could try deleting the Nvidia shader cache and then running the game normally. In this scenario we would expect very high CPU utilization the first time you load into a level, but only the first time.

Failing ...

4 hours ago, Malkdu said:

The hotfix made it unable to invite people to my dojo, gives me a Crossplay Error?

We are aware of invitations to your dojo failing with a crossplay error. This will be in our very next hotfix.  As a temporary workaround don't forget that you can trade in Maroo's Bazaar on Mars!

So, something super interesting, is the "Time added" label stuck to your screen.  I only see "Time added" at the very start of the mission if I destroy an orb while the tutorial tips are still on screen and then it goes away.  Can you get this problem to occur in a practice run?  Could you record the whole run *before* the problem occurs? 

Please don't necro 4 year old threads, it doesn't help us, and it doesn't help you either. The game evolves over time.  We need up to date information on how to reproduce bugs on the current live game, not repeat bumps of vague bugs that might be related but probably are not.

We are currently investigating some new issues with Transference after the Veilbreaker update that would affect client players especially if they have low-spec hardware or high ping.

The riven types that Palladino sells are random, and they appear to have no type in the shop for me.  It should tell you the broad type once you pay slivers for it.  If it said "rifle riven" in the list of offerings, before paying, then that would be a bug and we would need more steps for how you got to the point where the UI was giving false information.

You haven't submitted any crash reports to us.  It's very important to help improve the game, if you do crash, that you fill out the Crash Reporter and hit Send! Posting your "WAR number" (from the crash reporter) also makes discussion about specific problems easier

Video and logs would be helpful here. This all seemed to work properly here, where if your Shadow dies you are forced back to your warframe (if your warframe is still alive), or back to a grave stone and then observer mode (if it is not)

16 minutes ago, SadAt4AM said:

Still not fixed

Known, and fixed in our next update

7 minutes ago, Damocles said:

What about punch through on projectile weapons not going through walls and other objects?

Can we get an example of not working, please?

We're working on the problem.  For now, it looks like as a workaround if you open your chat from the chat line it works more reliably. Like this:

/w PersonName Hi there!

5 minutes ago, Mixnek said:

Not addressing the severe chat bug that was introduced with the Veilbreaker update?

It would be helpful to see your game logs. After trying and failing to chat with a person, close the game then send in your log files to Support please. If you open the launcher there is a Get Logs button under the "gear icon" configuration section.
(Your log files are deleted each time you start the game, so you would have to do this immediately after you see the chat problem)

Use the mouse and keyboard to subsume. There's an issue with PC players switching between keyboard and gamepad in menus that we're working on.

On 2022-09-09 at 11:49 AM, BruheTheWizard said:

how do i check if my CPU supports SSE?

The launcher will now warn you if your CPU doesn't meet the future minimum specifications. If you don't see a warning at game launch, then you are good!

1) The issue is fixed and will be going with the next hotfix.

2) There's basically nothing you can do to avoid the problem, it's an issue with the physics engine rather than anything the player is doing.

3) We don't need more logs/videos, but thanks!

We're aware of the problem with New War now, thanks everybody who submitted constructive and detailed reports. Especially those doing long-form videos of the entire mission so we can see the events leading up to the bug, and also those PC players who sent LOG FILES to support department. Super helpful!

(No we can't fix this at 8pm on sunday evening. But it's a top priority for the morning)

16 minutes ago, Marushinja said:

Okay I might have a development.

I tried again after seeing your reply and it still didn't work. However, I usually play using a USB gamepad (an xboxone pad if that matters). When I exited the Helminth and went back to it using mouse and keyboard, it suddenly worked again!

Aha! Yep there is it.  Thanks for the followup, I'll put out a bounty on that bug!

I made a copy of your account, and did not see a problem.  I was able to subsume both Ember (with the archon shard segment installed),  and Mag (without the archon shard segment).

Is this still a problem for anybody after updating to 32.0.2?

1 hour ago, XennethKeisere said:

You guys literally nerfed the throws. You didn't keep the full damage from charge throws at all!

The speargun throw now has the stats of a charged throw, without needing to charge it.  If you review the wiki you will see that the explosion of Javlok's charged throw is listed as 300 heat damage.... And in new update, the Javlok's throw damage explosion is 300 heat damage.

(modified by the amount of ammo still in the spear when you throw it, of course)

We don't see this happening.  Please supply more details, ideally a video, about exactly what you're doing when this happens.

Were you using Last Gasp by any chance?  There is a known bug where Last Gasp can result in a loss of function in conjunction with junction...fights.  We'll be disabling this in a future update